Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b867313d5da15d53a18133370a61a70433f711c397243b09ee99003a098749

Tx prefix hash: 949f2721fe7fb577f3ba32880d296e4354efea05311d06cf91b02711d52ef4d9
Tx public key: 884098759b8aba8aec90857f7c9999c5eb61f04d3f7bda99a6b711a5332030a0
Timestamp: 1707174492 Timestamp [UCT]: 2024-02-05 23:08:12 Age [y:d:h:m:s]: 01:064:15:48:31
Block: 951212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307277 RingCT/type: yes/0
Extra: 01884098759b8aba8aec90857f7c9999c5eb61f04d3f7bda99a6b711a5332030a00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 488eda427948ef96eb70b2cb1a8c6a202dd765c9375adbeb1f7d357a60d38fc3 0.600000000000 1409950 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": 951222, "vin": [ { "gen": { "height": 951212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "488eda427948ef96eb70b2cb1a8c6a202dd765c9375adbeb1f7d357a60d38fc3" } } ], "extra": [ 1, 136, 64, 152, 117, 155, 138, 186, 138, 236, 144, 133, 127, 124, 153, 153, 197, 235, 97, 240, 77, 63, 123, 218, 153, 166, 183, 17, 165, 51, 32, 48, 160, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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