Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3594997f70e35026fa9903a9c5959a513f6f8cc05194c5f02ce6b707d1e5ccc1

Tx prefix hash: 570bf73c1ddad61a0881a729c2a467b18e463d6579bc4c57c9355cd39c7c7817
Tx public key: 046999bf1a66295f0f161f25c5cd6af9884a8bfae8d645bda01e6a12df205d54
Timestamp: 1672827099 Timestamp [UCT]: 2023-01-04 10:11:39 Age [y:d:h:m:s]: 02:096:13:11:13
Block: 667339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590682 RingCT/type: yes/0
Extra: 01046999bf1a66295f0f161f25c5cd6af9884a8bfae8d645bda01e6a12df205d5402110000000233af99f4000000000000000000

1 output(s) for total of 3.774234051000 dcy

stealth address amount amount idx
00: 5ed0dd3fdb4135c6eec1220283034d498721ab842fed50e1876f6e1ca48949ff 3.774234051000 1108508 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": 667349, "vin": [ { "gen": { "height": 667339 } } ], "vout": [ { "amount": 3774234051, "target": { "key": "5ed0dd3fdb4135c6eec1220283034d498721ab842fed50e1876f6e1ca48949ff" } } ], "extra": [ 1, 4, 105, 153, 191, 26, 102, 41, 95, 15, 22, 31, 37, 197, 205, 106, 249, 136, 74, 139, 250, 232, 214, 69, 189, 160, 30, 106, 18, 223, 32, 93, 84, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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