Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 69a6657bc322f5e3dc4174f56752f46ea34abfd4ba6ea934ac5096d26d76b518

Tx prefix hash: 3ae03e03e201c1e28ceb80d6038acb0ec00976b381c7cfa1b62ac92197f6b16d
Tx public key: 36cae92cfbe7b3297dc19e4aaeca021ed6aaa71bea7a66fba6c3b2986edfe2ec
Timestamp: 1585241610 Timestamp [UCT]: 2020-03-26 16:53:30 Age [y:d:h:m:s]: 05:022:11:44:31
Block: 88407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174790 RingCT/type: yes/0
Extra: 0136cae92cfbe7b3297dc19e4aaeca021ed6aaa71bea7a66fba6c3b2986edfe2ec0211000000d045705818000000000000000000

1 output(s) for total of 312.659541830000 dcy

stealth address amount amount idx
00: 68e305a6d0a247aedd0d6d806dc84000f8065687a5975c5f17e31228d27b3859 312.659541830000 158947 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 88417, "vin": [ { "gen": { "height": 88407 } } ], "vout": [ { "amount": 312659541830, "target": { "key": "68e305a6d0a247aedd0d6d806dc84000f8065687a5975c5f17e31228d27b3859" } } ], "extra": [ 1, 54, 202, 233, 44, 251, 231, 179, 41, 125, 193, 158, 74, 174, 202, 2, 30, 214, 170, 167, 27, 234, 122, 102, 251, 166, 195, 178, 152, 110, 223, 226, 236, 2, 17, 0, 0, 0, 208, 69, 112, 88, 24, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8