Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d3483ca39167670907fefa91d1b2b4a388b8e6430259b06b8aaf13572c3803c

Tx prefix hash: 6d37409aac84efc0dd505b5eee4ddfefb7ae9dbfe2ea6070dba2d3d615768965
Tx public key: 24e0429b14f87ecb75c86d22609d5996817eaeeb2ea99af226ea26fe0e8a7ed4
Timestamp: 1730694549 Timestamp [UCT]: 2024-11-04 04:29:09 Age [y:d:h:m:s]: 00:225:08:14:08
Block: 1146136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160828 RingCT/type: yes/0
Extra: 0124e0429b14f87ecb75c86d22609d5996817eaeeb2ea99af226ea26fe0e8a7ed40211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb71a445c43a58f73ce6284bf07ed5068904330fcfb85fe3da52a19e4bfafd9a 0.600000000000 1630707 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": 1146146, "vin": [ { "gen": { "height": 1146136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb71a445c43a58f73ce6284bf07ed5068904330fcfb85fe3da52a19e4bfafd9a" } } ], "extra": [ 1, 36, 224, 66, 155, 20, 248, 126, 203, 117, 200, 109, 34, 96, 157, 89, 150, 129, 126, 174, 235, 46, 169, 154, 242, 38, 234, 38, 254, 14, 138, 126, 212, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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