Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b4484b385dd154bedbaa1162b4d347d47a2d5d0b3a87c0c6926b7b10ba671af

Tx prefix hash: 23f68659dee097060f2680fb8acbb20c84b4255160825ec831c354f86d5cbfdb
Tx public key: 55eab3e488e2bf3f243bad25fa4280f9bc0e1382e99c40e5848d918df04d7be7
Timestamp: 1699617043 Timestamp [UCT]: 2023-11-10 11:50:43 Age [y:d:h:m:s]: 01:195:23:51:58
Block: 888577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401293 RingCT/type: yes/0
Extra: 0155eab3e488e2bf3f243bad25fa4280f9bc0e1382e99c40e5848d918df04d7be702110000000633af99f4000000000000000000

1 output(s) for total of 0.697871613000 dcy

stealth address amount amount idx
00: f72288976abc2599f6875e207d71b50cb83a522022aac9796a399dd5892d3512 0.697871613000 1344524 of 0

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": 888587, "vin": [ { "gen": { "height": 888577 } } ], "vout": [ { "amount": 697871613, "target": { "key": "f72288976abc2599f6875e207d71b50cb83a522022aac9796a399dd5892d3512" } } ], "extra": [ 1, 85, 234, 179, 228, 136, 226, 191, 63, 36, 59, 173, 37, 250, 66, 128, 249, 188, 14, 19, 130, 233, 156, 64, 229, 132, 141, 145, 141, 240, 77, 123, 231, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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