Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58bac43e7b7b0d44a0fd52f3069c3a8131def649540e95e06559ba0678fe010a

Tx prefix hash: a839137ad2989c20044c2358491e018df2b5553e9ab8a28c23526a91e2ad2096
Tx public key: 17afc31ee46ea3745f0df65a88a2c8c271ddf87acd8358683dc207105424ea2a
Timestamp: 1718178299 Timestamp [UCT]: 2024-06-12 07:44:59 Age [y:d:h:m:s]: 00:227:22:32:25
Block: 1042461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163065 RingCT/type: yes/0
Extra: 0117afc31ee46ea3745f0df65a88a2c8c271ddf87acd8358683dc207105424ea2a021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1bfb055f3da191a971c3f1e9315f9815a1cedb01dd9885cd8632de767d80d56 0.600000000000 1511386 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": 1042471, "vin": [ { "gen": { "height": 1042461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1bfb055f3da191a971c3f1e9315f9815a1cedb01dd9885cd8632de767d80d56" } } ], "extra": [ 1, 23, 175, 195, 30, 228, 110, 163, 116, 95, 13, 246, 90, 136, 162, 200, 194, 113, 221, 248, 122, 205, 131, 88, 104, 61, 194, 7, 16, 84, 36, 234, 42, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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