Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105f0ec30854e1c60e89bd586efa3732c96995ac17d3b5659042fa331d7d7847

Tx prefix hash: c76716e4f9acdafbc11a81fae225a960ae5c0328cff97fa7ddc5b942d922e23f
Tx public key: f9f77f5598be212ae0d5804d2ea19910e5fb938d60937970977c4efb2fb032c2
Timestamp: 1705792479 Timestamp [UCT]: 2024-01-20 23:14:39 Age [y:d:h:m:s]: 01:139:03:47:55
Block: 939735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360606 RingCT/type: yes/0
Extra: 01f9f77f5598be212ae0d5804d2ea19910e5fb938d60937970977c4efb2fb032c20211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42361e883a4c57f5f44d4ee73fdf0e0239874f99087f17fbe279af50455ba101 0.600000000000 1397851 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": 939745, "vin": [ { "gen": { "height": 939735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42361e883a4c57f5f44d4ee73fdf0e0239874f99087f17fbe279af50455ba101" } } ], "extra": [ 1, 249, 247, 127, 85, 152, 190, 33, 42, 224, 213, 128, 77, 46, 161, 153, 16, 229, 251, 147, 141, 96, 147, 121, 112, 151, 124, 78, 251, 47, 176, 50, 194, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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