Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cacf95f92c9fd02a0da840e2ec8516c0abd2007c56dc54eafbd066f629786db

Tx prefix hash: de4e842249041d10ad64342defc8886a950e3fba77c6fcc42a6c52bcc5b0931a
Tx public key: 344f08a7b1d7f0d3fc3e0a4e991ff477c0449cdc9947e3f0fd4f8c0296d2096a
Timestamp: 1737652146 Timestamp [UCT]: 2025-01-23 17:09:06 Age [y:d:h:m:s]: 00:294:14:37:01
Block: 1203709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208101 RingCT/type: yes/0
Extra: 01344f08a7b1d7f0d3fc3e0a4e991ff477c0449cdc9947e3f0fd4f8c0296d2096a02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb4c750c5674cac62b66aefdcf0b34349b07cd14ef2a53b2dbba757deaa38e7c 0.600000000000 1690388 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": 1203719, "vin": [ { "gen": { "height": 1203709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb4c750c5674cac62b66aefdcf0b34349b07cd14ef2a53b2dbba757deaa38e7c" } } ], "extra": [ 1, 52, 79, 8, 167, 177, 215, 240, 211, 252, 62, 10, 78, 153, 31, 244, 119, 192, 68, 156, 220, 153, 71, 227, 240, 253, 79, 140, 2, 150, 210, 9, 106, 2, 17, 0, 0, 0, 13, 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