Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e8f8ed0b1c1fe7e8828f4c8c7110e58b613cf2a400923a83e938dfac07ac0c5

Tx prefix hash: 706e8aff196c1709446f13c5ed291f8f5cc5646e2e4ac9fadbf0f550dc449be6
Tx public key: 2117973de849384f4cfdd9831ae8ca24d71b283d46c7938cb40d2a229375c1b5
Timestamp: 1736669997 Timestamp [UCT]: 2025-01-12 08:19:57 Age [y:d:h:m:s]: 00:083:08:46:25
Block: 1195614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59364 RingCT/type: yes/0
Extra: 012117973de849384f4cfdd9831ae8ca24d71b283d46c7938cb40d2a229375c1b5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9bb78e0ecd0e10f2cb87589225ee40f4118e3ba5707ff748f07e8735d5300ec 0.600000000000 1682205 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": 1195624, "vin": [ { "gen": { "height": 1195614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9bb78e0ecd0e10f2cb87589225ee40f4118e3ba5707ff748f07e8735d5300ec" } } ], "extra": [ 1, 33, 23, 151, 61, 232, 73, 56, 79, 76, 253, 217, 131, 26, 232, 202, 36, 215, 27, 40, 61, 70, 199, 147, 140, 180, 13, 42, 34, 147, 117, 193, 181, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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