Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b247386131f288b99af624d14c140c63d244124574f20930454ee16f2eada5

Tx prefix hash: ca3b50e4a10dad0f608ac94432ea8abbbd0e295e3ef771c98a3cb076bc9c4972
Tx public key: 7b43733f354f49c5100e5181374a38b45dabe45e889841eefc9f85a354df2b01
Timestamp: 1707942910 Timestamp [UCT]: 2024-02-14 20:35:10 Age [y:d:h:m:s]: 01:049:05:43:59
Block: 957585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296225 RingCT/type: yes/0
Extra: 017b43733f354f49c5100e5181374a38b45dabe45e889841eefc9f85a354df2b0102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a861566f47706910a8f8e95440ae9d283e4eba533e145c1f3c1cd7bf07563a 0.600000000000 1416903 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": 957595, "vin": [ { "gen": { "height": 957585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a861566f47706910a8f8e95440ae9d283e4eba533e145c1f3c1cd7bf07563a" } } ], "extra": [ 1, 123, 67, 115, 63, 53, 79, 73, 197, 16, 14, 81, 129, 55, 74, 56, 180, 93, 171, 228, 94, 136, 152, 65, 238, 252, 159, 133, 163, 84, 223, 43, 1, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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