Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5236d6eb4e52083d87fd7aa611876612323a562f6e9cf239a520c0075e6cfc7

Tx prefix hash: 44c0d5fa8034d5f472a0663e0d4127f5560904f207f6a29b376fbc372a7ef316
Tx public key: 984fa15e93871058d24d9c40812fa1a0b74c9ee85e591b8b10378f65649fd08c
Timestamp: 1727396902 Timestamp [UCT]: 2024-09-27 00:28:22 Age [y:d:h:m:s]: 00:041:08:28:22
Block: 1118876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29545 RingCT/type: yes/0
Extra: 01984fa15e93871058d24d9c40812fa1a0b74c9ee85e591b8b10378f65649fd08c021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49d490d2e3c46812ef62aeda6eaa45e7cd4408732a68c52f6664d9041bcd7f93 0.600000000000 1600225 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": 1118886, "vin": [ { "gen": { "height": 1118876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49d490d2e3c46812ef62aeda6eaa45e7cd4408732a68c52f6664d9041bcd7f93" } } ], "extra": [ 1, 152, 79, 161, 94, 147, 135, 16, 88, 210, 77, 156, 64, 129, 47, 161, 160, 183, 76, 158, 232, 94, 89, 27, 139, 16, 55, 143, 101, 100, 159, 208, 140, 2, 17, 0, 0, 0, 8, 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