Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fb6b1be3e99e0d751d1365bea29cd2695bf01dae3437b2dce83f661d1f44571

Tx prefix hash: a9feb442492d45ac02748282fd95b3add806b5190cd186c313d6330c8a9d1811
Tx public key: 61baf8b085e5ac7d98a42755250274de7d8a17a114d020a832aa41e60056f722
Timestamp: 1729331292 Timestamp [UCT]: 2024-10-19 09:48:12 Age [y:d:h:m:s]: 00:200:12:50:00
Block: 1134912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143120 RingCT/type: yes/0
Extra: 0161baf8b085e5ac7d98a42755250274de7d8a17a114d020a832aa41e60056f7220211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c1b2cbb40dcaea19f7e6b5a006f9f79abcf4031086c94fa99168ac863302ca1 0.600000000000 1618239 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": 1134922, "vin": [ { "gen": { "height": 1134912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c1b2cbb40dcaea19f7e6b5a006f9f79abcf4031086c94fa99168ac863302ca1" } } ], "extra": [ 1, 97, 186, 248, 176, 133, 229, 172, 125, 152, 164, 39, 85, 37, 2, 116, 222, 125, 138, 23, 161, 20, 208, 32, 168, 50, 170, 65, 230, 0, 86, 247, 34, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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