Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d0322a5a6255af74211c100160a1a96c966c5ae9744cfd0677f4ae47dce202

Tx prefix hash: 138c28fd4333f78792e41092a98ec235c594269a73b8260c91a404c8f19f87e8
Tx public key: b7e9925fc2d3777a7204dffcbc4a225a540a8ff16f03d8e98ab45706822b009e
Timestamp: 1728949176 Timestamp [UCT]: 2024-10-14 23:39:36 Age [y:d:h:m:s]: 01:024:16:07:03
Block: 1131751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275992 RingCT/type: yes/0
Extra: 01b7e9925fc2d3777a7204dffcbc4a225a540a8ff16f03d8e98ab45706822b009e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d44c7735562f6e27262f47054d9fbc6b22addec08bff07dc1803eb6988aa9133 0.600000000000 1614656 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": 1131761, "vin": [ { "gen": { "height": 1131751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d44c7735562f6e27262f47054d9fbc6b22addec08bff07dc1803eb6988aa9133" } } ], "extra": [ 1, 183, 233, 146, 95, 194, 211, 119, 122, 114, 4, 223, 252, 188, 74, 34, 90, 84, 10, 143, 241, 111, 3, 216, 233, 138, 180, 87, 6, 130, 43, 0, 158, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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