Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88b20c930a598810c7db9186f57b574c3a3ebdc00480ebf944395e30f0f98489

Tx prefix hash: 8c1a990c6a4e95c1cb577ed1862f72f656f6a4008c47ba896eecb2610214ff19
Tx public key: 89ef4cb1b0f5efdf31793b5914fef8eeabb38409ceb238de8ce25ae603c317c3
Timestamp: 1731864899 Timestamp [UCT]: 2024-11-17 17:34:59 Age [y:d:h:m:s]: 00:124:18:46:37
Block: 1155831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88997 RingCT/type: yes/0
Extra: 0189ef4cb1b0f5efdf31793b5914fef8eeabb38409ceb238de8ce25ae603c317c30211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a877f071a763e5b5e8d420ed62f77347272515519bda53e93f85760a07132f2 0.600000000000 1641450 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": 1155841, "vin": [ { "gen": { "height": 1155831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a877f071a763e5b5e8d420ed62f77347272515519bda53e93f85760a07132f2" } } ], "extra": [ 1, 137, 239, 76, 177, 176, 245, 239, 223, 49, 121, 59, 89, 20, 254, 248, 238, 171, 179, 132, 9, 206, 178, 56, 222, 140, 226, 90, 230, 3, 195, 23, 195, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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