Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c9ebd6834bbe72aa0f63bee43b026095500b4dafc1e5e41817b0c2c89ad6fb

Tx prefix hash: c4982ef9fcd07124f9824757ac3930252d84a5240e7ac731b2d9c1fd8b8e7581
Tx public key: 75ce05e1788eb529b615c1639ba91a31d5da532230d638acb4c3fab3e0d7d37d
Timestamp: 1672720580 Timestamp [UCT]: 2023-01-03 04:36:20 Age [y:d:h:m:s]: 01:334:10:00:57
Block: 666450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500023 RingCT/type: yes/0
Extra: 0175ce05e1788eb529b615c1639ba91a31d5da532230d638acb4c3fab3e0d7d37d02110000000652542ceb000000000000000000

1 output(s) for total of 3.799920021000 dcy

stealth address amount amount idx
00: 331be810ecd60d63e4592353671052357190571bdb07e7b002be5e4e80f8f11a 3.799920021000 1107561 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": 666460, "vin": [ { "gen": { "height": 666450 } } ], "vout": [ { "amount": 3799920021, "target": { "key": "331be810ecd60d63e4592353671052357190571bdb07e7b002be5e4e80f8f11a" } } ], "extra": [ 1, 117, 206, 5, 225, 120, 142, 181, 41, 182, 21, 193, 99, 155, 169, 26, 49, 213, 218, 83, 34, 48, 214, 56, 172, 180, 195, 250, 179, 224, 215, 211, 125, 2, 17, 0, 0, 0, 6, 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