Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b13f12d93dd5fc22755b3e256ef156f25df6a602d46767b46f0612388b3730ca

Tx prefix hash: 51a1a1577bdc89372b43fcdb7c212830f1d539a6e1c0cc4aa983fbe3eafbb32a
Tx public key: 772c48941ed71512a02c9c0240db8bd1b6e37fb8f2d657cfba32d79866033d0e
Timestamp: 1737053725 Timestamp [UCT]: 2025-01-16 18:55:25 Age [y:d:h:m:s]: 00:150:19:36:13
Block: 1198789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107513 RingCT/type: yes/0
Extra: 01772c48941ed71512a02c9c0240db8bd1b6e37fb8f2d657cfba32d79866033d0e021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6a8457745431d6a76594ef5fccd007b1fa95c30424e0c0b93dfc191e6e0cc6 0.600000000000 1685416 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": 1198799, "vin": [ { "gen": { "height": 1198789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6a8457745431d6a76594ef5fccd007b1fa95c30424e0c0b93dfc191e6e0cc6" } } ], "extra": [ 1, 119, 44, 72, 148, 30, 215, 21, 18, 160, 44, 156, 2, 64, 219, 139, 209, 182, 227, 127, 184, 242, 214, 87, 207, 186, 50, 215, 152, 102, 3, 61, 14, 2, 17, 0, 0, 0, 8, 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