Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 729d304587b8fb0eab052cf5bedfc9f3694ff83fcb457ef63922b8c8e533acb7

Tx prefix hash: 836ffa23bd0999211bb76f07c3b82d4f56fde58b6eef07386b344a038b124b14
Tx public key: 7ee206e5d9757982561d0f9998769516de474a8d3dfc079948abddea840be95e
Timestamp: 1721998312 Timestamp [UTC]: 2024-07-26 12:51:52 Age [y:d:h:m:s]: 01:291:19:53:23
Block: 1074125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459354 RingCT/type: yes/0
Extra: 017ee206e5d9757982561d0f9998769516de474a8d3dfc079948abddea840be95e021100000005e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e611e45f8c33c56884e182bfbdb85e1e2eb2cbfe1bdbf5f23e5121658e83b231 0.000600000000 1546638 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 dinastycoin-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": 1074135, "vin": [ { "gen": { "height": 1074125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e611e45f8c33c56884e182bfbdb85e1e2eb2cbfe1bdbf5f23e5121658e83b231" } } ], "extra": [ 1, 126, 226, 6, 229, 217, 117, 121, 130, 86, 29, 15, 153, 152, 118, 149, 22, 222, 71, 74, 141, 61, 252, 7, 153, 72, 171, 221, 234, 132, 11, 233, 94, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: