Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e9634b923ff23472c640abdc3a251ced60810916df64aefc4ed1934a929a04

Tx prefix hash: 28734cedd6219bbd04f620b3eda92de11d4308c5aeb4baeca4538bc4d6243be7
Tx public key: 2316395ee2c52fdc437b95cb0cf1479df7670204e0c453e7bf9c4fc3adc4e6ba
Timestamp: 1699095977 Timestamp [UCT]: 2023-11-04 11:06:17 Age [y:d:h:m:s]: 01:078:00:07:37
Block: 884459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316918 RingCT/type: yes/0
Extra: 012316395ee2c52fdc437b95cb0cf1479df7670204e0c453e7bf9c4fc3adc4e6ba02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.720145386000 dcy

stealth address amount amount idx
00: b4b55dd5c8ac8138a8b4f042fe2e38e291ba740fcff14719f1860f8f93cf7fa8 0.720145386000 1340202 of 0

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": 884469, "vin": [ { "gen": { "height": 884459 } } ], "vout": [ { "amount": 720145386, "target": { "key": "b4b55dd5c8ac8138a8b4f042fe2e38e291ba740fcff14719f1860f8f93cf7fa8" } } ], "extra": [ 1, 35, 22, 57, 94, 226, 197, 47, 220, 67, 123, 149, 203, 12, 241, 71, 157, 247, 103, 2, 4, 224, 196, 83, 231, 191, 156, 79, 195, 173, 196, 230, 186, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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