Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e197afe29050210748108e7475f6cb348f394ff88a885fcb8a20ef6d12d2357

Tx prefix hash: 7afe9e0ff863bb1fe4e3b550b04e0f9882b4ac19a7f43d086fa381b9bf35fa68
Tx public key: 7e76140445950bdc51e82c282f82add45b3ea3c6fa62a5efd88da09e8295fe10
Timestamp: 1722860041 Timestamp [UCT]: 2024-08-05 12:14:01 Age [y:d:h:m:s]: 01:096:06:40:26
Block: 1081264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327291 RingCT/type: yes/0
Extra: 017e76140445950bdc51e82c282f82add45b3ea3c6fa62a5efd88da09e8295fe10021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf8ea4789b972dcd1593845cf860fe5e22fcd5d9ebf25caa4eab7c4ab0bc63b 0.600000000000 1554943 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": 1081274, "vin": [ { "gen": { "height": 1081264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf8ea4789b972dcd1593845cf860fe5e22fcd5d9ebf25caa4eab7c4ab0bc63b" } } ], "extra": [ 1, 126, 118, 20, 4, 69, 149, 11, 220, 81, 232, 44, 40, 47, 130, 173, 212, 91, 62, 163, 198, 250, 98, 165, 239, 216, 141, 160, 158, 130, 149, 254, 16, 2, 17, 0, 0, 0, 5, 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