Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f670c16c8be60f7d4f70a6819575f15895bf4a2df0f3234ad57e2fe800472f9b

Tx prefix hash: aa55652728777672d152e4802a0c0275c5ac32c39c4edc14a729a2423fa8f6dc
Tx public key: e7b617a743add632f496963f51e86136479dc682e32dfe8bccc583cbb87516fd
Timestamp: 1717178419 Timestamp [UCT]: 2024-05-31 18:00:19 Age [y:d:h:m:s]: 00:225:06:57:47
Block: 1034167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161229 RingCT/type: yes/0
Extra: 01e7b617a743add632f496963f51e86136479dc682e32dfe8bccc583cbb87516fd02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb82b064717c90078214ec89469a523ff384c3e474b4ea01819a9e6b5d6b3cc7 0.600000000000 1502652 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": 1034177, "vin": [ { "gen": { "height": 1034167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb82b064717c90078214ec89469a523ff384c3e474b4ea01819a9e6b5d6b3cc7" } } ], "extra": [ 1, 231, 182, 23, 167, 67, 173, 214, 50, 244, 150, 150, 63, 81, 232, 97, 54, 71, 157, 198, 130, 227, 45, 254, 139, 204, 197, 131, 203, 184, 117, 22, 253, 2, 17, 0, 0, 0, 10, 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