Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd29a7fd991c72e377722ba6ca1a4558705b44e1a898a34ed450e52abd93f4d

Tx prefix hash: 1b6ae7a3d7a5beacee0de98afdf865f37d249fc8383cc1e3a5598e3284e99c8e
Tx public key: cf3c6429ec69ab35b82937d947aa33cfb90de9512308059da80a951662637495
Timestamp: 1681023470 Timestamp [UCT]: 2023-04-09 06:57:50 Age [y:d:h:m:s]: 02:018:14:32:23
Block: 734699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535438 RingCT/type: yes/0
Extra: 01cf3c6429ec69ab35b82937d947aa33cfb90de9512308059da80a951662637495021100000003b3164c24000000000000000000

1 output(s) for total of 2.257550378000 dcy

stealth address amount amount idx
00: 6fe188ba75ab0f6d58879728e8130aeae3e970f796e7c47bd1e603d985f040c1 2.257550378000 1180944 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": 734709, "vin": [ { "gen": { "height": 734699 } } ], "vout": [ { "amount": 2257550378, "target": { "key": "6fe188ba75ab0f6d58879728e8130aeae3e970f796e7c47bd1e603d985f040c1" } } ], "extra": [ 1, 207, 60, 100, 41, 236, 105, 171, 53, 184, 41, 55, 217, 71, 170, 51, 207, 185, 13, 233, 81, 35, 8, 5, 157, 168, 10, 149, 22, 98, 99, 116, 149, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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