Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f27af98194f0a0b82685a54827b02521c405ff83e0ebaba70bae5eaef89718bf

Tx prefix hash: cc1113a8446c6b80799742ae4bbcd50c94bbcce330cd506ee586a81a6de1bb7c
Tx public key: 8d2ccdf38a892431aa9773a0e85b5db25503e38863cbede8c2a17323eb289b7d
Timestamp: 1736891461 Timestamp [UCT]: 2025-01-14 21:51:01 Age [y:d:h:m:s]: 00:155:01:56:07
Block: 1197444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110531 RingCT/type: yes/0
Extra: 018d2ccdf38a892431aa9773a0e85b5db25503e38863cbede8c2a17323eb289b7d021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e48ffe70c7cd81d7610fca29922e6e1dc34a859d5f71c49530d092dc24d6a9d 0.600000000000 1684051 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": 1197454, "vin": [ { "gen": { "height": 1197444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e48ffe70c7cd81d7610fca29922e6e1dc34a859d5f71c49530d092dc24d6a9d" } } ], "extra": [ 1, 141, 44, 205, 243, 138, 137, 36, 49, 170, 151, 115, 160, 232, 91, 93, 178, 85, 3, 227, 136, 99, 203, 237, 232, 194, 161, 115, 35, 235, 40, 155, 125, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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