Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7bc40e21edcfba69af3eeef58294735361617c43131659f663c0ab873537e30

Tx prefix hash: c8d7ff6df919a32730324de062172485c65f0bf5dacbc27f23bb5ae333fac635
Tx public key: 68c19e4e0bd983ef65e615c5a2ad505359cbcb9a335c4c58868b8d1729fbdd90
Timestamp: 1721906401 Timestamp [UCT]: 2024-07-25 11:20:01 Age [y:d:h:m:s]: 00:325:18:28:11
Block: 1073357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232686 RingCT/type: yes/0
Extra: 0168c19e4e0bd983ef65e615c5a2ad505359cbcb9a335c4c58868b8d1729fbdd90021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e0e4e9a08406c3e6bed33f0d470ce8311a9ac71ceb2e2fda9400302bcc03aab 0.600000000000 1545858 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": 1073367, "vin": [ { "gen": { "height": 1073357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e0e4e9a08406c3e6bed33f0d470ce8311a9ac71ceb2e2fda9400302bcc03aab" } } ], "extra": [ 1, 104, 193, 158, 78, 11, 217, 131, 239, 101, 230, 21, 197, 162, 173, 80, 83, 89, 203, 203, 154, 51, 92, 76, 88, 134, 139, 141, 23, 41, 251, 221, 144, 2, 17, 0, 0, 0, 21, 233, 20, 221, 21, 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