Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d10be72c050aac62f56d7a4477d5f103838aad355581a22d1a3ded6a17fafe6

Tx prefix hash: f36551cfff4898952d5a0f9d1d8aeb998a182101e5dd016dd88c81c8f355858d
Tx public key: f4e4de18f89eca9b9de65782ee9ad69a743a9016da04ca1a0fa01e12ee4d1e5a
Timestamp: 1719565871 Timestamp [UCT]: 2024-06-28 09:11:11 Age [y:d:h:m:s]: 00:240:00:45:12
Block: 1053951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171474 RingCT/type: yes/0
Extra: 01f4e4de18f89eca9b9de65782ee9ad69a743a9016da04ca1a0fa01e12ee4d1e5a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30062c5d1e64c6f89d44a6a7081154d692b724b2ef5a616be8db148e2bff2f80 0.600000000000 1524306 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": 1053961, "vin": [ { "gen": { "height": 1053951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30062c5d1e64c6f89d44a6a7081154d692b724b2ef5a616be8db148e2bff2f80" } } ], "extra": [ 1, 244, 228, 222, 24, 248, 158, 202, 155, 157, 230, 87, 130, 238, 154, 214, 154, 116, 58, 144, 22, 218, 4, 202, 26, 15, 160, 30, 18, 238, 77, 30, 90, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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