Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81443cd7da06d8630764b23d612e72cc2360a1d93fba5904a18c2bc82fc0f6e7

Tx prefix hash: 905fe0eb50069603dcdfb271d2899f0d4142421a183b729594f1729462dded9b
Tx public key: d308f110f96c4aa30254141f834d581aa4d3e38c41088aa026aa002aef9cc57b
Timestamp: 1712578214 Timestamp [UCT]: 2024-04-08 12:10:14 Age [y:d:h:m:s]: 01:211:12:29:21
Block: 995997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409853 RingCT/type: yes/0
Extra: 01d308f110f96c4aa30254141f834d581aa4d3e38c41088aa026aa002aef9cc57b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adf627160fe2d7a2749773be71122ec08ee46b0c9554b698feb08a4110641b4d 0.600000000000 1456413 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": 996007, "vin": [ { "gen": { "height": 995997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adf627160fe2d7a2749773be71122ec08ee46b0c9554b698feb08a4110641b4d" } } ], "extra": [ 1, 211, 8, 241, 16, 249, 108, 74, 163, 2, 84, 20, 31, 131, 77, 88, 26, 164, 211, 227, 140, 65, 8, 138, 160, 38, 170, 0, 42, 239, 156, 197, 123, 2, 17, 0, 0, 0, 7, 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