Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557d4882f2a342d23bdc2df80982169294d8b83d6cbab8e0b5aece1b9bf087f9

Tx prefix hash: eb58488c374bd1cd8c9de7dec843501219d72190c2e9e95822812d34b9b76667
Tx public key: cfdeb6c63c939476eae03bd1a1fc5c92ee9830f6b130af57dd0437374a5a3b0d
Timestamp: 1739834887 Timestamp [UCT]: 2025-02-17 23:28:07 Age [y:d:h:m:s]: 00:276:02:11:30
Block: 1221523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195095 RingCT/type: yes/0
Extra: 01cfdeb6c63c939476eae03bd1a1fc5c92ee9830f6b130af57dd0437374a5a3b0d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb2341f4cedda52ec01f0f9a132a48a0267e32306133ac6526dc384bc6130dc 0.600000000000 1708368 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": 1221533, "vin": [ { "gen": { "height": 1221523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb2341f4cedda52ec01f0f9a132a48a0267e32306133ac6526dc384bc6130dc" } } ], "extra": [ 1, 207, 222, 182, 198, 60, 147, 148, 118, 234, 224, 59, 209, 161, 252, 92, 146, 238, 152, 48, 246, 177, 48, 175, 87, 221, 4, 55, 55, 74, 90, 59, 13, 2, 17, 0, 0, 0, 6, 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