Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b4462da39dfca138ecbf7dc4cd57b9e3e2f64e002ecc09e1635f0fe143f7a97

Tx prefix hash: beb8dcae1a82a1a730ce1beb1c557eb7b49f6724127e96a8f77d6bc8b3f04a20
Tx public key: 17f691233f9c3b9e55ea15e9131f37aaaf19593c937d3ed76b4674f2bc307b6d
Timestamp: 1628034030 Timestamp [UCT]: 2021-08-03 23:40:30 Age [y:d:h:m:s]: 03:286:07:40:13
Block: 306838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977174 RingCT/type: yes/0
Extra: 0117f691233f9c3b9e55ea15e9131f37aaaf19593c937d3ed76b4674f2bc307b6d02110000007506faf294000000000000000000

1 output(s) for total of 59.063450093000 dcy

stealth address amount amount idx
00: 6a73632f0c1f90c34d58192713680e117b8179037f729753dda9b2947e628ebe 59.063450093000 639783 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": 306848, "vin": [ { "gen": { "height": 306838 } } ], "vout": [ { "amount": 59063450093, "target": { "key": "6a73632f0c1f90c34d58192713680e117b8179037f729753dda9b2947e628ebe" } } ], "extra": [ 1, 23, 246, 145, 35, 63, 156, 59, 158, 85, 234, 21, 233, 19, 31, 55, 170, 175, 25, 89, 60, 147, 125, 62, 215, 107, 70, 116, 242, 188, 48, 123, 109, 2, 17, 0, 0, 0, 117, 6, 250, 242, 148, 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