Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ac5458d5ba77377fc329c2d9ac9e96216c0b7e5fc2821b5177f77983e7f2a7

Tx prefix hash: dd27b967bde8635ff27dd0f6ad042179fa97141d3866829f56177ccb626005e9
Tx public key: 49d22ac3d1a121208f014b2515d1a6601db5d690668d3b1e4b47a45459add5f5
Timestamp: 1727367552 Timestamp [UCT]: 2024-09-26 16:19:12 Age [y:d:h:m:s]: 00:199:21:22:08
Block: 1118635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142676 RingCT/type: yes/0
Extra: 0149d22ac3d1a121208f014b2515d1a6601db5d690668d3b1e4b47a45459add5f502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f135bbc0a4a519bbe3616684a221a8313056d2f272675c9f549d2d23644f454d 0.600000000000 1599896 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": 1118645, "vin": [ { "gen": { "height": 1118635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f135bbc0a4a519bbe3616684a221a8313056d2f272675c9f549d2d23644f454d" } } ], "extra": [ 1, 73, 210, 42, 195, 209, 161, 33, 32, 143, 1, 75, 37, 21, 209, 166, 96, 29, 181, 214, 144, 102, 141, 59, 30, 75, 71, 164, 84, 89, 173, 213, 245, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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