Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3cf870fe4231c86fb057f030e333a282551ec866e2145f49b70b0f5412f52d3

Tx prefix hash: f8979306b1e9bac5fa9f1554bb50bcabffcb3c938368fee89850c8b5edee3752
Tx public key: 15e493998403c57aa90480c05b489e280d96d61c868fe86ac13ee298a2d91a6e
Timestamp: 1736585258 Timestamp [UTC]: 2025-01-11 08:47:38 Age [y:d:h:m:s]: 01:313:20:11:54
Block: 1194919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488259 RingCT/type: yes/0
Extra: 0115e493998403c57aa90480c05b489e280d96d61c868fe86ac13ee298a2d91a6e021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cfeb4174e4c25e263a8924d3f07706cb7532098627b2a6da4aa9a43f4a0d3201 0.000600000000 1681498 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": 1194929, "vin": [ { "gen": { "height": 1194919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfeb4174e4c25e263a8924d3f07706cb7532098627b2a6da4aa9a43f4a0d3201" } } ], "extra": [ 1, 21, 228, 147, 153, 132, 3, 197, 122, 169, 4, 128, 192, 91, 72, 158, 40, 13, 150, 214, 28, 134, 143, 232, 106, 193, 62, 226, 152, 162, 217, 26, 110, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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: