Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1f5ddb829c21ff57fe57d277106d07056a38de1a0b584e986a7d44278b549e9

Tx prefix hash: 06b4ca136e39a1f85ebafb72fd5c6df1bc6dc64876edeca227957c1c3a676dff
Tx public key: a0780a8d941abf3e3f825cae548faec21bdaf2d531d1dc35607fa2fc82421427
Timestamp: 1738081436 Timestamp [UCT]: 2025-01-28 16:23:56 Age [y:d:h:m:s]: 00:297:08:04:11
Block: 1207048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210259 RingCT/type: yes/0
Extra: 01a0780a8d941abf3e3f825cae548faec21bdaf2d531d1dc35607fa2fc82421427021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f06854d45c5a87c45bb3313a4de83ca8337c367c2c1fb49e4eecb719640b2afa 0.600000000000 1693769 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": 1207058, "vin": [ { "gen": { "height": 1207048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f06854d45c5a87c45bb3313a4de83ca8337c367c2c1fb49e4eecb719640b2afa" } } ], "extra": [ 1, 160, 120, 10, 141, 148, 26, 191, 62, 63, 130, 92, 174, 84, 143, 174, 194, 27, 218, 242, 213, 49, 209, 220, 53, 96, 127, 162, 252, 130, 66, 20, 39, 2, 17, 0, 0, 0, 6, 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