Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 930f1e073e057a36b70075432d094428b250ee39bb041ead2651dc273f646279

Tx prefix hash: f662608294945b6bb6b81e4990ed99ba743a3d00e0ba746d3be717992432b703
Tx public key: b2a0091e65c765d278bf3d23991c46f6acf2b7bc38f8c1bdd85fc2c2d9892cf8
Timestamp: 1702817777 Timestamp [UCT]: 2023-12-17 12:56:17 Age [y:d:h:m:s]: 01:337:10:48:17
Block: 915100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500047 RingCT/type: yes/0
Extra: 01b2a0091e65c765d278bf3d23991c46f6acf2b7bc38f8c1bdd85fc2c2d9892cf8021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c842391ae8f6a24491338a9cbdf71a5002a64cc4837d99eea357839a1793f1a 0.600000000000 1372482 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": 915110, "vin": [ { "gen": { "height": 915100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c842391ae8f6a24491338a9cbdf71a5002a64cc4837d99eea357839a1793f1a" } } ], "extra": [ 1, 178, 160, 9, 30, 101, 199, 101, 210, 120, 191, 61, 35, 153, 28, 70, 246, 172, 242, 183, 188, 56, 248, 193, 189, 216, 95, 194, 194, 217, 137, 44, 248, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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