Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ffbf7f6f742847beb903249068d61a31f62ac280fa953896f9a0c0d84e7e51

Tx prefix hash: 8174c604881bcbabdc6d75c4332b02c3e6f534da11ddc5bda0f98ce70d80eb3e
Tx public key: f5fde1c2a8db438320e5b98b62141e8d5fc4078358541e1673fb1f3743c3794b
Timestamp: 1709173482 Timestamp [UCT]: 2024-02-29 02:24:42 Age [y:d:h:m:s]: 01:077:20:48:38
Block: 967802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316677 RingCT/type: yes/0
Extra: 01f5fde1c2a8db438320e5b98b62141e8d5fc4078358541e1673fb1f3743c3794b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3614459a7fad7a84fa1778ee88726cc3f32f1dda48f7029b35ed0aa074e59de9 0.600000000000 1427587 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": 967812, "vin": [ { "gen": { "height": 967802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3614459a7fad7a84fa1778ee88726cc3f32f1dda48f7029b35ed0aa074e59de9" } } ], "extra": [ 1, 245, 253, 225, 194, 168, 219, 67, 131, 32, 229, 185, 139, 98, 20, 30, 141, 95, 196, 7, 131, 88, 84, 30, 22, 115, 251, 31, 55, 67, 195, 121, 75, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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