Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb15430bd7b9d17bc2113bd65f56f5d97966a036779fe31736aa24c2e1eb3c8

Tx prefix hash: a16618004c573d193dc47162d77005d164bd71a3ca7749a28a25db61bc3b3af4
Tx public key: b3c3f5698a12c7d9bdf0b6a41bada78051c614dedff4070ccc3aeeb63421a3e0
Timestamp: 1734991746 Timestamp [UCT]: 2024-12-23 22:09:06 Age [y:d:h:m:s]: 00:095:01:37:45
Block: 1181734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67718 RingCT/type: yes/0
Extra: 01b3c3f5698a12c7d9bdf0b6a41bada78051c614dedff4070ccc3aeeb63421a3e00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ae6a879feb2871f0e42d97f67954b651ba93a5fe418bd90cfefedf522ea6f87 0.600000000000 1668159 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": 1181744, "vin": [ { "gen": { "height": 1181734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae6a879feb2871f0e42d97f67954b651ba93a5fe418bd90cfefedf522ea6f87" } } ], "extra": [ 1, 179, 195, 245, 105, 138, 18, 199, 217, 189, 240, 182, 164, 27, 173, 167, 128, 81, 198, 20, 222, 223, 244, 7, 12, 204, 58, 238, 182, 52, 33, 163, 224, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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