Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d96b84957bda1d052c2af60ec36eaac6821a6638703b78a6a493d9f79aac2448

Tx prefix hash: b3d3e1c1110a6c57e4ed60748af806be69b367ae5a2600fb0e6ccf2b5737dc62
Tx public key: 960fd8d890076ff981e2c941e71abce901f49862ef888c965e712935d5d7ab55
Timestamp: 1673058522 Timestamp [UCT]: 2023-01-07 02:28:42 Age [y:d:h:m:s]: 02:053:15:05:41
Block: 669238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559992 RingCT/type: yes/0
Extra: 01960fd8d890076ff981e2c941e71abce901f49862ef888c965e712935d5d7ab5502110000000152542ceb000000000000000000

1 output(s) for total of 3.719946127000 dcy

stealth address amount amount idx
00: 1a08577c431683f68bb5d4e20247e6ef53d4edb282b360c42b908b59f0fd7ba2 3.719946127000 1110541 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": 669248, "vin": [ { "gen": { "height": 669238 } } ], "vout": [ { "amount": 3719946127, "target": { "key": "1a08577c431683f68bb5d4e20247e6ef53d4edb282b360c42b908b59f0fd7ba2" } } ], "extra": [ 1, 150, 15, 216, 216, 144, 7, 111, 249, 129, 226, 201, 65, 231, 26, 188, 233, 1, 244, 152, 98, 239, 136, 140, 150, 94, 113, 41, 53, 213, 215, 171, 85, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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