Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77966d01c5772122f0af9c670c270b474a1c9730f267c588453c8268471aea13

Tx prefix hash: 6a6192677ea6616c42682a78691b2ee2fd77bb9d8e2d27e93895b5e1b6ba821c
Tx public key: 4b1d27a73acc26db1c9440f8f5cc4e9b089d3c086cf97ddb5bdb4042f0794a92
Timestamp: 1737906183 Timestamp [UCT]: 2025-01-26 15:43:03 Age [y:d:h:m:s]: 00:328:19:05:16
Block: 1205809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232578 RingCT/type: yes/0
Extra: 014b1d27a73acc26db1c9440f8f5cc4e9b089d3c086cf97ddb5bdb4042f0794a92021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e6499d6cfc00f3f3d4e684d4ea13374d744b9d7ed4f35c1bed7ccd6074032d1 0.600000000000 1692508 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": 1205819, "vin": [ { "gen": { "height": 1205809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e6499d6cfc00f3f3d4e684d4ea13374d744b9d7ed4f35c1bed7ccd6074032d1" } } ], "extra": [ 1, 75, 29, 39, 167, 58, 204, 38, 219, 28, 148, 64, 248, 245, 204, 78, 155, 8, 157, 60, 8, 108, 249, 125, 219, 91, 219, 64, 66, 240, 121, 74, 146, 2, 17, 0, 0, 0, 5, 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