Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b63aeea24088b8087c07cceb5f6537d1461f442e09a86a0c420003f6022636ce

Tx prefix hash: a34e533955b9fd7e7c3969cf6b236aff2edbf137af5d866819d2f083076b9c9b
Tx public key: f1df5d481da6d155fd16e329a47995cbc00a7c0e8311199e3e57d50c870277a4
Timestamp: 1705351150 Timestamp [UCT]: 2024-01-15 20:39:10 Age [y:d:h:m:s]: 01:086:15:29:55
Block: 936094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323037 RingCT/type: yes/0
Extra: 01f1df5d481da6d155fd16e329a47995cbc00a7c0e8311199e3e57d50c870277a402110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffc4a48708f357cd17a6d8ad8942757b90e534f3b8430905f138220d26cdd09d 0.600000000000 1394116 of 15

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": 936104, "vin": [ { "gen": { "height": 936094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffc4a48708f357cd17a6d8ad8942757b90e534f3b8430905f138220d26cdd09d" } } ], "extra": [ 1, 241, 223, 93, 72, 29, 166, 209, 85, 253, 22, 227, 41, 164, 121, 149, 203, 192, 10, 124, 14, 131, 17, 25, 158, 62, 87, 213, 12, 135, 2, 119, 164, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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