Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acbf0f253bfb38e85c5131c753ba9543416b6952093df449a596f75df1ae612e

Tx prefix hash: fccb86261942dc5542bd2a9d9055a8efe7b2a4c19c9c955abdce47d1151840b4
Tx public key: 331f30f5b668b1a2186e76a72932493527971c30213e3d7761ea03ae88200248
Timestamp: 1730212439 Timestamp [UCT]: 2024-10-29 14:33:59 Age [y:d:h:m:s]: 00:141:08:53:11
Block: 1142149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100883 RingCT/type: yes/0
Extra: 01331f30f5b668b1a2186e76a72932493527971c30213e3d7761ea03ae88200248021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a30ae156e23edaaa12d85d80ab3b511c585351b3cae8cc0e467f6de0afd05c3 0.600000000000 1625990 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": 1142159, "vin": [ { "gen": { "height": 1142149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a30ae156e23edaaa12d85d80ab3b511c585351b3cae8cc0e467f6de0afd05c3" } } ], "extra": [ 1, 51, 31, 48, 245, 182, 104, 177, 162, 24, 110, 118, 167, 41, 50, 73, 53, 39, 151, 28, 48, 33, 62, 61, 119, 97, 234, 3, 174, 136, 32, 2, 72, 2, 17, 0, 0, 0, 2, 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