Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf3289b6313e7ad3c42a4788bb895703cf2378b2038b194c13a72c362ad40e2

Tx prefix hash: f6336bbd9c9a5ac56f4f2dc6df461ed6a14a7693987b802f84754a5dccf916e6
Tx public key: 0c89381904a97262f446e9a56f64b0d1870fec192ea76e16ff9e306d86d3e980
Timestamp: 1730812237 Timestamp [UCT]: 2024-11-05 13:10:37 Age [y:d:h:m:s]: 00:140:14:41:35
Block: 1147102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100315 RingCT/type: yes/0
Extra: 010c89381904a97262f446e9a56f64b0d1870fec192ea76e16ff9e306d86d3e98002110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e47b294c8949fd5df12c91e6280b05bdc2e3b1d9065d637bcc5f10336f9f0ba6 0.600000000000 1631795 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": 1147112, "vin": [ { "gen": { "height": 1147102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e47b294c8949fd5df12c91e6280b05bdc2e3b1d9065d637bcc5f10336f9f0ba6" } } ], "extra": [ 1, 12, 137, 56, 25, 4, 169, 114, 98, 244, 70, 233, 165, 111, 100, 176, 209, 135, 15, 236, 25, 46, 167, 110, 22, 255, 158, 48, 109, 134, 211, 233, 128, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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