Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88412033c08bccc1253326b75f5726b9c4cfb3c30491ff6c5ca34cf8a16db77d

Tx prefix hash: 3622bddae9697e760995273b0c400fc5048f2c53e753988d477ea6839803780d
Tx public key: f1381f061397fa8dfcf3a17b8b023cee6df08bea9177cad69b6fa3b016e24f46
Timestamp: 1685863059 Timestamp [UCT]: 2023-06-04 07:17:39 Age [y:d:h:m:s]: 01:341:14:57:50
Block: 774789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505371 RingCT/type: yes/0
Extra: 01f1381f061397fa8dfcf3a17b8b023cee6df08bea9177cad69b6fa3b016e24f46021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.662656673000 dcy

stealth address amount amount idx
00: 6f8ed81a64a1d2004579a1a3b9547f1a01dd8e02b9d8b4371615091ff7adfd2a 1.662656673000 1224276 of 0

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": 774799, "vin": [ { "gen": { "height": 774789 } } ], "vout": [ { "amount": 1662656673, "target": { "key": "6f8ed81a64a1d2004579a1a3b9547f1a01dd8e02b9d8b4371615091ff7adfd2a" } } ], "extra": [ 1, 241, 56, 31, 6, 19, 151, 250, 141, 252, 243, 161, 123, 139, 2, 60, 238, 109, 240, 139, 234, 145, 119, 202, 214, 155, 111, 163, 176, 22, 226, 79, 70, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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