Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20a0be9e4fc1f15b2a30cee130ba2f3c852b4d073abadb8464f6f246a85faaf9

Tx prefix hash: df4eed3891336397b1da321fedabdae20fb31fde562611a2390f599dca08cc7f
Tx public key: 0053a00f1faaa166ae366f143059646b232cd2f091b4800a4baa2320d76b3bb1
Timestamp: 1710783920 Timestamp [UCT]: 2024-03-18 17:45:20 Age [y:d:h:m:s]: 01:045:15:56:29
Block: 981172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293620 RingCT/type: yes/0
Extra: 010053a00f1faaa166ae366f143059646b232cd2f091b4800a4baa2320d76b3bb102110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 806d95a8dfbe629f905ce025250f3c164124acae63f2dee3e03d6b43a7db7535 0.600000000000 1441265 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": 981182, "vin": [ { "gen": { "height": 981172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "806d95a8dfbe629f905ce025250f3c164124acae63f2dee3e03d6b43a7db7535" } } ], "extra": [ 1, 0, 83, 160, 15, 31, 170, 161, 102, 174, 54, 111, 20, 48, 89, 100, 107, 35, 44, 210, 240, 145, 180, 128, 10, 75, 170, 35, 32, 215, 107, 59, 177, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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