Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9227e540076f3ab0d04d43c428268d0f0167feaded036f1055dac5defabb26c6

Tx prefix hash: f4f466c363243e080e1dcce30bd4a52aac00c35ca48d4e5dff82b5b3a19281d1
Tx public key: 4267aaede1499253dbc743c036da1f3c47af4dc2f73c8902747e386c975c2ad1
Timestamp: 1736901869 Timestamp [UCT]: 2025-01-15 00:44:29 Age [y:d:h:m:s]: 00:154:17:58:29
Block: 1197534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110293 RingCT/type: yes/0
Extra: 014267aaede1499253dbc743c036da1f3c47af4dc2f73c8902747e386c975c2ad1021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dc154280bc484ba911b74c6dc47f1c75f80cd418b95ea42cc23671ee43492fb 0.600000000000 1684145 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": 1197544, "vin": [ { "gen": { "height": 1197534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dc154280bc484ba911b74c6dc47f1c75f80cd418b95ea42cc23671ee43492fb" } } ], "extra": [ 1, 66, 103, 170, 237, 225, 73, 146, 83, 219, 199, 67, 192, 54, 218, 31, 60, 71, 175, 77, 194, 247, 60, 137, 2, 116, 126, 56, 108, 151, 92, 42, 209, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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