Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eae0e01d7e650169de6ea7f4fc849629129ca4e3527c8aba4dea61d490915ab1

Tx prefix hash: 780f8c1058f833fd278f32db2fac845009fc8c13f4df519c716e9a3d1afe8d66
Tx public key: 6ff8ad9f032b91fee65ec430359500ddd38282474c6284c9148ce26e64c2a42f
Timestamp: 1715110448 Timestamp [UCT]: 2024-05-07 19:34:08 Age [y:d:h:m:s]: 00:324:18:06:21
Block: 1017022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232133 RingCT/type: yes/0
Extra: 016ff8ad9f032b91fee65ec430359500ddd38282474c6284c9148ce26e64c2a42f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8330e71ce321aae93cbd0c01607f39b51d77842fa1b653fd24401e2fbe857ad 0.600000000000 1480777 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": 1017032, "vin": [ { "gen": { "height": 1017022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8330e71ce321aae93cbd0c01607f39b51d77842fa1b653fd24401e2fbe857ad" } } ], "extra": [ 1, 111, 248, 173, 159, 3, 43, 145, 254, 230, 94, 196, 48, 53, 149, 0, 221, 211, 130, 130, 71, 76, 98, 132, 201, 20, 140, 226, 110, 100, 194, 164, 47, 2, 17, 0, 0, 0, 3, 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