Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1917c05e6e014078687c12f792c1b6fb1e3f4cffa2215acb2cd422f6746912

Tx prefix hash: 81e6278b1c246bf8e8de08ad6ad0f2aa64be36a8e99c38b9a4277804cc7403ae
Tx public key: 2924f1cc4565bb80864fc67e6b7b27f25e8cc047bfb118f1bf9ba84b05763148
Timestamp: 1676812017 Timestamp [UCT]: 2023-02-19 13:06:57 Age [y:d:h:m:s]: 02:073:12:55:52
Block: 700383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574174 RingCT/type: yes/0
Extra: 012924f1cc4565bb80864fc67e6b7b27f25e8cc047bfb118f1bf9ba84b0576314802110000000374b6d784000000000000000000

1 output(s) for total of 2.933190643000 dcy

stealth address amount amount idx
00: 421fabfe35b93e165a9a7484c29336368e969bcc5da30c562a90a11b46598b91 2.933190643000 1143824 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": 700393, "vin": [ { "gen": { "height": 700383 } } ], "vout": [ { "amount": 2933190643, "target": { "key": "421fabfe35b93e165a9a7484c29336368e969bcc5da30c562a90a11b46598b91" } } ], "extra": [ 1, 41, 36, 241, 204, 69, 101, 187, 128, 134, 79, 198, 126, 107, 123, 39, 242, 94, 140, 192, 71, 191, 177, 24, 241, 191, 155, 168, 75, 5, 118, 49, 72, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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