Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd52228defb5ddeb782e9cbb220054f5f365c2398ad031d5dfb8b5391f063371

Tx prefix hash: 44a1cacdcea1108fe697a2a38e6af1612bbb8d82ef599834145caa3df1589463
Tx public key: e10848a79dfe950f46d42c718b196b9024124810e1758270308480ce073e5b45
Timestamp: 1583528296 Timestamp [UCT]: 2020-03-06 20:58:16 Age [y:d:h:m:s]: 05:262:06:31:42
Block: 77561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1340559 RingCT/type: yes/0
Extra: 01e10848a79dfe950f46d42c718b196b9024124810e1758270308480ce073e5b4502110000000b4ac5aa02000000000000000000

1 output(s) for total of 339.632313481000 dcy

stealth address amount amount idx
00: 685ba9c634e416bc6f1c5c0fe7b9fabc748ea504981d06a00d7bb0aa8f55aca3 339.632313481000 142702 of 0

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": 77571, "vin": [ { "gen": { "height": 77561 } } ], "vout": [ { "amount": 339632313481, "target": { "key": "685ba9c634e416bc6f1c5c0fe7b9fabc748ea504981d06a00d7bb0aa8f55aca3" } } ], "extra": [ 1, 225, 8, 72, 167, 157, 254, 149, 15, 70, 212, 44, 113, 139, 25, 107, 144, 36, 18, 72, 16, 225, 117, 130, 112, 48, 132, 128, 206, 7, 62, 91, 69, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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