Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1080f2553dd2e8c92ce2a2cc280e7ffef591232072a594c6f1d16228dfe7ac13

Tx prefix hash: 7bf83ade154af167f6020047c66a0c41f00edb3a60401d6ff0863b0fec2a89b0
Tx public key: 7a6507e4a74fe1ebbaec35d7f4c23d4a88f8bee035e49a99bac12b3be875da67
Timestamp: 1735670812 Timestamp [UCT]: 2024-12-31 18:46:52 Age [y:d:h:m:s]: 00:098:01:24:01
Block: 1187342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69864 RingCT/type: yes/0
Extra: 017a6507e4a74fe1ebbaec35d7f4c23d4a88f8bee035e49a99bac12b3be875da670211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e558cb4ac67443d278fff88a724b96a5893be04bbf1ba3459b7c502c1cb823 0.600000000000 1673831 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": 1187352, "vin": [ { "gen": { "height": 1187342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e558cb4ac67443d278fff88a724b96a5893be04bbf1ba3459b7c502c1cb823" } } ], "extra": [ 1, 122, 101, 7, 228, 167, 79, 225, 235, 186, 236, 53, 215, 244, 194, 61, 74, 136, 248, 190, 224, 53, 228, 154, 153, 186, 193, 43, 59, 232, 117, 218, 103, 2, 17, 0, 0, 0, 4, 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