Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52cb740fde0996ae1b13182996fe538758fc5d9e2d2de0c0039cfe7e95aa26e

Tx prefix hash: 1fef9555d4033730095dcc77b34fd51772b59a25ae5925f6aaf3bd4f2f5a9a22
Tx public key: 98acc5bc3950f16546d015b5fc0ad5588ca6c9eb0cea62279929d41eef89542f
Timestamp: 1717405685 Timestamp [UCT]: 2024-06-03 09:08:05 Age [y:d:h:m:s]: 01:182:16:09:50
Block: 1036060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389160 RingCT/type: yes/0
Extra: 0198acc5bc3950f16546d015b5fc0ad5588ca6c9eb0cea62279929d41eef89542f02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3a89e003542aa43a7e51d06e9a243f5df03976f4ce543ce0e8520b67ed94062 0.600000000000 1504585 of 15

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": 1036070, "vin": [ { "gen": { "height": 1036060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3a89e003542aa43a7e51d06e9a243f5df03976f4ce543ce0e8520b67ed94062" } } ], "extra": [ 1, 152, 172, 197, 188, 57, 80, 241, 101, 70, 208, 21, 181, 252, 10, 213, 88, 140, 166, 201, 235, 12, 234, 98, 39, 153, 41, 212, 30, 239, 137, 84, 47, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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