Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c44a35d2e7eb462564127e3a16241edb1a32a0e21fa76f6d818ef468e26989

Tx prefix hash: 268040c8174723c1881e40525f2aea3dceba013be5ccbae1f0a63fa5c63ecde6
Tx public key: dac67872dce88ae845b47927f0f3a74746c3ce5eb2c002fc7426ddabb531c820
Timestamp: 1709142189 Timestamp [UCT]: 2024-02-28 17:43:09 Age [y:d:h:m:s]: 01:277:09:29:36
Block: 967547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457009 RingCT/type: yes/0
Extra: 01dac67872dce88ae845b47927f0f3a74746c3ce5eb2c002fc7426ddabb531c82002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3c9f4879e9f1dd88b48f9eabea40a3877726dea9cb5be8e5094bcd67c9a9908 0.600000000000 1427330 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": 967557, "vin": [ { "gen": { "height": 967547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3c9f4879e9f1dd88b48f9eabea40a3877726dea9cb5be8e5094bcd67c9a9908" } } ], "extra": [ 1, 218, 198, 120, 114, 220, 232, 138, 232, 69, 180, 121, 39, 240, 243, 167, 71, 70, 195, 206, 94, 178, 192, 2, 252, 116, 38, 221, 171, 181, 49, 200, 32, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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