Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45281c7c97acb38a30e290b72b97cf8964e97351669724e7b887955950e5e1c9

Tx prefix hash: 758a1b7a4f423eaa7b6a8787007924e12be19888ff1955fbe4a8ca519901446c
Tx public key: 8efc61efbc6a4fb38a0a2a26f41d53e8e53ab77c9150df24184d3ec595ad6230
Timestamp: 1716958847 Timestamp [UCT]: 2024-05-29 05:00:47 Age [y:d:h:m:s]: 00:155:19:40:45
Block: 1032344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111539 RingCT/type: yes/0
Extra: 018efc61efbc6a4fb38a0a2a26f41d53e8e53ab77c9150df24184d3ec595ad62300211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbd37bdcc76d1355cb733b0cd5f626cecf1a450fb42008dd67a2c39d7664a234 0.600000000000 1500797 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": 1032354, "vin": [ { "gen": { "height": 1032344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbd37bdcc76d1355cb733b0cd5f626cecf1a450fb42008dd67a2c39d7664a234" } } ], "extra": [ 1, 142, 252, 97, 239, 188, 106, 79, 179, 138, 10, 42, 38, 244, 29, 83, 232, 229, 58, 183, 124, 145, 80, 223, 36, 24, 77, 62, 197, 149, 173, 98, 48, 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