Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faa84bf88081fdc927cfe8142c90ca4f62e28afdfec2ce9e275dd769e8650d45

Tx prefix hash: e1e8cc5e8f001703f199ae6ba5ce6697d6df990917e21d972e8799de32934f06
Tx public key: 4631c9f6dce4e1581dbeb5f6daa1a9554ab944245ca087448efe1a15d1019ed9
Timestamp: 1739801904 Timestamp [UCT]: 2025-02-17 14:18:24 Age [y:d:h:m:s]: 00:344:14:34:47
Block: 1221256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243980 RingCT/type: yes/0
Extra: 014631c9f6dce4e1581dbeb5f6daa1a9554ab944245ca087448efe1a15d1019ed9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d36f26d6a77365d7838b5f736f3d33f51c7e5ddbac2074ca44b093cf63c9e17 0.600000000000 1708101 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": 1221266, "vin": [ { "gen": { "height": 1221256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d36f26d6a77365d7838b5f736f3d33f51c7e5ddbac2074ca44b093cf63c9e17" } } ], "extra": [ 1, 70, 49, 201, 246, 220, 228, 225, 88, 29, 190, 181, 246, 218, 161, 169, 85, 74, 185, 68, 36, 92, 160, 135, 68, 142, 254, 26, 21, 209, 1, 158, 217, 2, 17, 0, 0, 0, 1, 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