Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b50244873f56cf8bca336f6c119e74a88d680f919a730a3ecbcca9c128d0b5c

Tx prefix hash: 432235f338acb303086381ab951bd5ea8355ebfc7077ad000893e9d931938c3d
Tx public key: 15e9149b02a913f28aa4a0f59f25bb98ff6aad81a461cb21427f199842cdb814
Timestamp: 1719162496 Timestamp [UCT]: 2024-06-23 17:08:16 Age [y:d:h:m:s]: 00:326:06:53:36
Block: 1050597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233189 RingCT/type: yes/0
Extra: 0115e9149b02a913f28aa4a0f59f25bb98ff6aad81a461cb21427f199842cdb814021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df63fa135e1e93a7b89eaa6a906a243cf7b2bce3ed91224d464095fb60dd087f 0.600000000000 1520772 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": 1050607, "vin": [ { "gen": { "height": 1050597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df63fa135e1e93a7b89eaa6a906a243cf7b2bce3ed91224d464095fb60dd087f" } } ], "extra": [ 1, 21, 233, 20, 155, 2, 169, 19, 242, 138, 164, 160, 245, 159, 37, 187, 152, 255, 106, 173, 129, 164, 97, 203, 33, 66, 127, 25, 152, 66, 205, 184, 20, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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