Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 104f973a1916d2ba99322da3b1a62c3f16a6514381e5d6a745f7da3d58250075

Tx prefix hash: 70c81b707e0b2345452b819981506db6088c16feafd9b50deba5195a68ee3058
Tx public key: 0e6739d3111e9c4fb714520e18e637d58a5a05e7ab2f0e273636bee8cdbc62e7
Timestamp: 1704464436 Timestamp [UCT]: 2024-01-05 14:20:36 Age [y:d:h:m:s]: 01:091:14:01:16
Block: 928746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326566 RingCT/type: yes/0
Extra: 010e6739d3111e9c4fb714520e18e637d58a5a05e7ab2f0e273636bee8cdbc62e70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f76c50c12b8626ddfd5eb75f48d8585c89a17df14a1e3720fd2fc9c289c9fc1 0.600000000000 1386606 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": 928756, "vin": [ { "gen": { "height": 928746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f76c50c12b8626ddfd5eb75f48d8585c89a17df14a1e3720fd2fc9c289c9fc1" } } ], "extra": [ 1, 14, 103, 57, 211, 17, 30, 156, 79, 183, 20, 82, 14, 24, 230, 55, 213, 138, 90, 5, 231, 171, 47, 14, 39, 54, 54, 190, 232, 205, 188, 98, 231, 2, 17, 0, 0, 0, 3, 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