Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9672b6b6c8180184134ebb9b032984c76f6b33710fef82eb3ff61bc68b6efb3

Tx prefix hash: 10010babb0fb3bf2a157f44a6d56b06822a2173ef59b243158e4b23a92c59e5d
Tx public key: 5440416efcda1dd67c62e725310cc8ed62a9e04cea96453b63bb9c8afc5f3c24
Timestamp: 1712172674 Timestamp [UCT]: 2024-04-03 19:31:14 Age [y:d:h:m:s]: 01:263:06:30:03
Block: 992629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446929 RingCT/type: yes/0
Extra: 015440416efcda1dd67c62e725310cc8ed62a9e04cea96453b63bb9c8afc5f3c2402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b21b2a4ad2e89638786f180a276ff8efc2b566e93d89fb2c4c2c44f27d3a490 0.600000000000 1452997 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": 992639, "vin": [ { "gen": { "height": 992629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b21b2a4ad2e89638786f180a276ff8efc2b566e93d89fb2c4c2c44f27d3a490" } } ], "extra": [ 1, 84, 64, 65, 110, 252, 218, 29, 214, 124, 98, 231, 37, 49, 12, 200, 237, 98, 169, 224, 76, 234, 150, 69, 59, 99, 187, 156, 138, 252, 95, 60, 36, 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