Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 448409202622c00791db97d43c7b2a9bf1eeb14bd38a6283e3afeb2c0240b3b3

Tx prefix hash: 57c1ac72051c8e4f656fe94a55be472d8bcce33a8663757a046301ef5deea311
Tx public key: 5b92532dbda01f70cd95e1861c929f7f0bc6a5ef9d99643c111579a8559f3f7f
Timestamp: 1702941688 Timestamp [UCT]: 2023-12-18 23:21:28 Age [y:d:h:m:s]: 01:186:09:11:29
Block: 916133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394206 RingCT/type: yes/0
Extra: 015b92532dbda01f70cd95e1861c929f7f0bc6a5ef9d99643c111579a8559f3f7f02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ee9bcc5653e389e9e6c604eb2d28f5a60b85ee3474e232b5b0544b3d366d4cf 0.600000000000 1373611 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": 916143, "vin": [ { "gen": { "height": 916133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ee9bcc5653e389e9e6c604eb2d28f5a60b85ee3474e232b5b0544b3d366d4cf" } } ], "extra": [ 1, 91, 146, 83, 45, 189, 160, 31, 112, 205, 149, 225, 134, 28, 146, 159, 127, 11, 198, 165, 239, 157, 153, 100, 60, 17, 21, 121, 168, 85, 159, 63, 127, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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