Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 905e1c26539dba725ec34f580aba72699e8ab8f5146bfc6b378b253a234e2e07

Tx prefix hash: 0f687f2a7d76b7f011cb3b5875c306b695b3509ee30e922880a6e839b4547b36
Tx public key: 6bfb5f86effa52e0742dc37d4127402cf21ad59c3db0ab688ad5a37a76d6f968
Timestamp: 1723560133 Timestamp [UCT]: 2024-08-13 14:42:13 Age [y:d:h:m:s]: 00:149:12:53:11
Block: 1087075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106964 RingCT/type: yes/0
Extra: 016bfb5f86effa52e0742dc37d4127402cf21ad59c3db0ab688ad5a37a76d6f968021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f384668960ad660e0b151f4aff5b8c0b6fcd0c98b178ce2687b3b609cc931508 0.600000000000 1561680 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": 1087085, "vin": [ { "gen": { "height": 1087075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f384668960ad660e0b151f4aff5b8c0b6fcd0c98b178ce2687b3b609cc931508" } } ], "extra": [ 1, 107, 251, 95, 134, 239, 250, 82, 224, 116, 45, 195, 125, 65, 39, 64, 44, 242, 26, 213, 156, 61, 176, 171, 104, 138, 213, 163, 122, 118, 214, 249, 104, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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