Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e76fc21737343c622889898b1063d59a3594f2e526142863bf7eed3b4457fdb5

Tx prefix hash: e888453c94690fdfda36d1ae62a2e7d7f6ae97e33e42f43cef7014c2a2d71a5c
Tx public key: b5c2d27eb30950fd89a87ffa35e6aaf24388e8f04b7297724083d2b6e578cd16
Timestamp: 1730972780 Timestamp [UCT]: 2024-11-07 09:46:20 Age [y:d:h:m:s]: 00:016:22:10:13
Block: 1148437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12114 RingCT/type: yes/0
Extra: 01b5c2d27eb30950fd89a87ffa35e6aaf24388e8f04b7297724083d2b6e578cd160211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d94f29bc61f043f3e043dd0d5eefd271d40f20ae504216a1f6cd28ac10dfaf4b 0.600000000000 1633280 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": 1148447, "vin": [ { "gen": { "height": 1148437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d94f29bc61f043f3e043dd0d5eefd271d40f20ae504216a1f6cd28ac10dfaf4b" } } ], "extra": [ 1, 181, 194, 210, 126, 179, 9, 80, 253, 137, 168, 127, 250, 53, 230, 170, 242, 67, 136, 232, 240, 75, 114, 151, 114, 64, 131, 210, 182, 229, 120, 205, 22, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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