Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c8e71d21d763faaba85968176bd30490adc86596a4e5a7c48cd8263fd26db2f

Tx prefix hash: 2eb1f9702e481b60af5786aa691a086b74b4bee8aa12cbba225cde6d659f054f
Tx public key: fabbdf8e0aef75e7357e99a5f8defbd427b3c98e9f9f5e155c3eb1389edaa2bf
Timestamp: 1734964918 Timestamp [UCT]: 2024-12-23 14:41:58 Age [y:d:h:m:s]: 00:100:00:47:17
Block: 1181531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71254 RingCT/type: yes/0
Extra: 01fabbdf8e0aef75e7357e99a5f8defbd427b3c98e9f9f5e155c3eb1389edaa2bf0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da03acc3e2a95bbc972fbda089220fe65f0bad8d9cf1f27620cb44b0a2a6b46f 0.600000000000 1667956 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": 1181541, "vin": [ { "gen": { "height": 1181531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da03acc3e2a95bbc972fbda089220fe65f0bad8d9cf1f27620cb44b0a2a6b46f" } } ], "extra": [ 1, 250, 187, 223, 142, 10, 239, 117, 231, 53, 126, 153, 165, 248, 222, 251, 212, 39, 179, 201, 142, 159, 159, 94, 21, 92, 62, 177, 56, 158, 218, 162, 191, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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