Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481ab5bf84f2bd7aca8f908fe45f9232ff8e48afb1c6eaa3a0cf440f5918ac17

Tx prefix hash: b22cac121bba7cd787cbb78f7aa6c9d24bdb3b09faa037a81fcda10a5686ae7e
Tx public key: 99f06838dcd3b2d5de14922a4f0a8c3bd70860d7af64f9d9b51dfeaeeabb688d
Timestamp: 1737042891 Timestamp [UCT]: 2025-01-16 15:54:51 Age [y:d:h:m:s]: 00:339:10:48:43
Block: 1198699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240166 RingCT/type: yes/0
Extra: 0199f06838dcd3b2d5de14922a4f0a8c3bd70860d7af64f9d9b51dfeaeeabb688d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21ae5dba880e5072b6042f5cd578f29a47333e25f45e20635c6e6ae149a10904 0.600000000000 1685324 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": 1198709, "vin": [ { "gen": { "height": 1198699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21ae5dba880e5072b6042f5cd578f29a47333e25f45e20635c6e6ae149a10904" } } ], "extra": [ 1, 153, 240, 104, 56, 220, 211, 178, 213, 222, 20, 146, 42, 79, 10, 140, 59, 215, 8, 96, 215, 175, 100, 249, 217, 181, 29, 254, 174, 234, 187, 104, 141, 2, 17, 0, 0, 0, 1, 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