Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cb71d2165fb8a118921e6681711bb9423bc1fd73dbd39c8cf002b0e5f4e49ee

Tx prefix hash: 71657189ea80ea07374a0a5fe241c8d584398992747363e6bca84985ac7f3fa8
Tx public key: 651cc98e8486801bcd734e8e89f15ea3dffcc7ac9d1bd5ad0aa55af4926f4603
Timestamp: 1626738610 Timestamp [UCT]: 2021-07-19 23:50:10 Age [y:d:h:m:s]: 03:280:05:01:03
Block: 297225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 971693 RingCT/type: yes/0
Extra: 01651cc98e8486801bcd734e8e89f15ea3dffcc7ac9d1bd5ad0aa55af4926f460302110000000fed79a617000000000000000000

1 output(s) for total of 63.560917748000 dcy

stealth address amount amount idx
00: a68584f0e002df2738f5f3053c91c02a76db00bd979ccf3ee227f61657af3b3a 63.560917748000 622117 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": 297235, "vin": [ { "gen": { "height": 297225 } } ], "vout": [ { "amount": 63560917748, "target": { "key": "a68584f0e002df2738f5f3053c91c02a76db00bd979ccf3ee227f61657af3b3a" } } ], "extra": [ 1, 101, 28, 201, 142, 132, 134, 128, 27, 205, 115, 78, 142, 137, 241, 94, 163, 223, 252, 199, 172, 157, 27, 213, 173, 10, 165, 90, 244, 146, 111, 70, 3, 2, 17, 0, 0, 0, 15, 237, 121, 166, 23, 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