Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c0aadd3ed7821047902045f923bbf3518359d81c6f537bfe8d158c143eca8f5

Tx prefix hash: cf22da41a6e2dfe62a1670e5d14d0b0f057d2b44b01c8db54a849c7eccca2163
Tx public key: 435953720306a6632afbd2e17af348d9498f5c1e3c3f15192be19f383fccab25
Timestamp: 1770085540 Timestamp [UTC]: 2026-02-03 02:25:40 Age [y:d:h:m:s]: 00:013:18:29:11
Block: 1469466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9830 RingCT/type: yes/0
Extra: 01435953720306a6632afbd2e17af348d9498f5c1e3c3f15192be19f383fccab25021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a90c2e7f29c31710cc63f9e06a7570a2e8c4b437e8ba47ccabf00d56568bf04d 0.000600000000 1958724 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": 1469476, "vin": [ { "gen": { "height": 1469466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a90c2e7f29c31710cc63f9e06a7570a2e8c4b437e8ba47ccabf00d56568bf04d" } } ], "extra": [ 1, 67, 89, 83, 114, 3, 6, 166, 99, 42, 251, 210, 225, 122, 243, 72, 217, 73, 143, 92, 30, 60, 63, 21, 25, 43, 225, 159, 56, 63, 204, 171, 37, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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) | dinastycoin version: tesla-369