Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00de8f94633901a17c23d3a64f9eee1b0573cb3485e300e51a6ad1e610298af0

Tx prefix hash: 116fecaba7af3bc4d9862e6a83f5f00b847196cb3aa2719c48c0794f0c711244
Tx public key: 7c71dc92e7cce1f6bf8e80bd8df3a50fbd4b9255e18daa77b9582398f6635106
Timestamp: 1723000574 Timestamp [UCT]: 2024-08-07 03:16:14 Age [y:d:h:m:s]: 00:251:03:26:18
Block: 1082431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179383 RingCT/type: yes/0
Extra: 017c71dc92e7cce1f6bf8e80bd8df3a50fbd4b9255e18daa77b9582398f6635106021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c4870b7998dbd3787d5319add5712202d6caf5ef0c405b6470fa5279f20470a 0.600000000000 1556258 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": 1082441, "vin": [ { "gen": { "height": 1082431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c4870b7998dbd3787d5319add5712202d6caf5ef0c405b6470fa5279f20470a" } } ], "extra": [ 1, 124, 113, 220, 146, 231, 204, 225, 246, 191, 142, 128, 189, 141, 243, 165, 15, 189, 75, 146, 85, 225, 141, 170, 119, 185, 88, 35, 152, 246, 99, 81, 6, 2, 17, 0, 0, 0, 5, 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