Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dcd189abb3757c44e11395300a0e74c2825a6b614c15a4fb3221cd0002da0d9

Tx prefix hash: 636c36d0f7fed2922ba26f5d37107e3c961b5c6190ed1cf3c52467a2c9b0c851
Tx public key: cd12a2cd5c693b1b2308a4f399acdf641f5be06a6a4e546949047fecd7b6c595
Timestamp: 1695924174 Timestamp [UCT]: 2023-09-28 18:02:54 Age [y:d:h:m:s]: 01:173:05:24:16
Block: 858158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384875 RingCT/type: yes/0
Extra: 01cd12a2cd5c693b1b2308a4f399acdf641f5be06a6a4e546949047fecd7b6c595021100000002faf35c9c000000000000000000

1 output(s) for total of 0.880169575000 dcy

stealth address amount amount idx
00: 26fe5a8591fec1a2531dfdec8c03ff9e7d58326af45009586029092a8d4e169e 0.880169575000 1312322 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": 858168, "vin": [ { "gen": { "height": 858158 } } ], "vout": [ { "amount": 880169575, "target": { "key": "26fe5a8591fec1a2531dfdec8c03ff9e7d58326af45009586029092a8d4e169e" } } ], "extra": [ 1, 205, 18, 162, 205, 92, 105, 59, 27, 35, 8, 164, 243, 153, 172, 223, 100, 31, 91, 224, 106, 106, 78, 84, 105, 73, 4, 127, 236, 215, 182, 197, 149, 2, 17, 0, 0, 0, 2, 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