Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dc0d4fcbd687090e0ee4214a89b33d7fe5a71733702756428587530f71dd88e

Tx prefix hash: 2fa5e6f717d96ca542412e95db5db05b90c91c30807889a33ad0f9f51d71ba9a
Tx public key: db2104d4c37949a4e7feb480e4b01b067de281effcf4d3755c43635cf71d9c2d
Timestamp: 1727470724 Timestamp [UCT]: 2024-09-27 20:58:44 Age [y:d:h:m:s]: 00:192:17:03:06
Block: 1119493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137532 RingCT/type: yes/0
Extra: 01db2104d4c37949a4e7feb480e4b01b067de281effcf4d3755c43635cf71d9c2d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73e4917ef3bc7e1d3cb01e0156a7acc0e5fcb5d8f5f600ee115891f32366bf68 0.600000000000 1601068 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": 1119503, "vin": [ { "gen": { "height": 1119493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73e4917ef3bc7e1d3cb01e0156a7acc0e5fcb5d8f5f600ee115891f32366bf68" } } ], "extra": [ 1, 219, 33, 4, 212, 195, 121, 73, 164, 231, 254, 180, 128, 228, 176, 27, 6, 125, 226, 129, 239, 252, 244, 211, 117, 92, 67, 99, 92, 247, 29, 156, 45, 2, 17, 0, 0, 0, 4, 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