Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c396c82416af429e5c18376e2f426eeed701c6d0339501f402fd7d7c53c6360

Tx prefix hash: e4960f8f3da11a306cbe4cad99ad45c5f325a67dfab8b7e24584f74f831df079
Tx public key: aebda938710d08e1eec1831c9f18a412290a164e337cd328e82e4c5b4faed480
Timestamp: 1705410214 Timestamp [UCT]: 2024-01-16 13:03:34 Age [y:d:h:m:s]: 00:359:10:27:27
Block: 936571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257355 RingCT/type: yes/0
Extra: 01aebda938710d08e1eec1831c9f18a412290a164e337cd328e82e4c5b4faed4800211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4cc794d1159a83fe8762807e1dd8666563f071541dba7fb95e01b85cf621290 0.600000000000 1394599 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": 936581, "vin": [ { "gen": { "height": 936571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4cc794d1159a83fe8762807e1dd8666563f071541dba7fb95e01b85cf621290" } } ], "extra": [ 1, 174, 189, 169, 56, 113, 13, 8, 225, 238, 193, 131, 28, 159, 24, 164, 18, 41, 10, 22, 78, 51, 124, 211, 40, 232, 46, 76, 91, 79, 174, 212, 128, 2, 17, 0, 0, 0, 5, 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