Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94e787c9bd8ed61f8304abc3ee58e02ac9a8414eb9776c49dfd8ce8b08dd9dcf

Tx prefix hash: 1f3570ec89b5902e0d380c1bb84ee08aab732de213b8fb7997a6f30b59c672ff
Tx public key: a5175c78b30f19848283b390d11bc81e2c3bb86be5ca61e834dc2071e024fa92
Timestamp: 1719579110 Timestamp [UCT]: 2024-06-28 12:51:50 Age [y:d:h:m:s]: 01:133:12:59:57
Block: 1054064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353982 RingCT/type: yes/0
Extra: 01a5175c78b30f19848283b390d11bc81e2c3bb86be5ca61e834dc2071e024fa9202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a4eb0f3e5f2c283bc26b5908777b19f4a3c1a499aea325bcfa421ef2faa24a8 0.600000000000 1524423 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": 1054074, "vin": [ { "gen": { "height": 1054064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a4eb0f3e5f2c283bc26b5908777b19f4a3c1a499aea325bcfa421ef2faa24a8" } } ], "extra": [ 1, 165, 23, 92, 120, 179, 15, 25, 132, 130, 131, 179, 144, 209, 27, 200, 30, 44, 59, 184, 107, 229, 202, 97, 232, 52, 220, 32, 113, 224, 36, 250, 146, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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