Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010823d08590f1f27e6017a0e2053996abaf2d9e4b79ebf9d5cf74b933980408

Tx prefix hash: 5fb7492d6676e998fb3cfac20b99e5dd6b5e6bcf26946b9b2b5c554c6011a358
Tx public key: 8b86521cfde3b02a6f2e5b3b6084ed1bdf228d4b3b7dfa5122c93976c5091035
Timestamp: 1736906820 Timestamp [UCT]: 2025-01-15 02:07:00 Age [y:d:h:m:s]: 00:154:21:38:08
Block: 1197567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110407 RingCT/type: yes/0
Extra: 018b86521cfde3b02a6f2e5b3b6084ed1bdf228d4b3b7dfa5122c93976c5091035021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc7e9d2f9f6a7d45981ea08a1cfee378fc7d100b4a5d0aed9a333bd946ae668f 0.600000000000 1684180 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": 1197577, "vin": [ { "gen": { "height": 1197567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc7e9d2f9f6a7d45981ea08a1cfee378fc7d100b4a5d0aed9a333bd946ae668f" } } ], "extra": [ 1, 139, 134, 82, 28, 253, 227, 176, 42, 111, 46, 91, 59, 96, 132, 237, 27, 223, 34, 141, 75, 59, 125, 250, 81, 34, 201, 57, 118, 197, 9, 16, 53, 2, 17, 0, 0, 0, 3, 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