Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc52f73152a2dc7edaa63401bf11898d549a06d977a3cf4e03f9e0fd1e4bfe2

Tx prefix hash: 870727350faf3e054cee73f3860dfe7700ed96518b75cf6960cb6eeb17d960ea
Tx public key: 967db2acbcdf4b1d98ef69f564ee8e86d1d0e9d419421b310942e07b2367c87a
Timestamp: 1736068030 Timestamp [UCT]: 2025-01-05 09:07:10 Age [y:d:h:m:s]: 00:127:21:19:28
Block: 1190645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91190 RingCT/type: yes/0
Extra: 01967db2acbcdf4b1d98ef69f564ee8e86d1d0e9d419421b310942e07b2367c87a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0968d7fbdac19b9e6b48160babac7d95d50d1cc4f62db3f7659168ae537824 0.600000000000 1677162 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": 1190655, "vin": [ { "gen": { "height": 1190645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0968d7fbdac19b9e6b48160babac7d95d50d1cc4f62db3f7659168ae537824" } } ], "extra": [ 1, 150, 125, 178, 172, 188, 223, 75, 29, 152, 239, 105, 245, 100, 238, 142, 134, 209, 208, 233, 212, 25, 66, 27, 49, 9, 66, 224, 123, 35, 103, 200, 122, 2, 17, 0, 0, 0, 2, 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