Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acce0a11ea12fa3ee1c65bd01b2f6e3fc1f4113184cdc7b69d550f16ff9788c5

Tx prefix hash: 1e7273c9c1b73b6f5bb2ff439ddc81116603a299d755885b2079cd5e2779a8b2
Tx public key: 44e5022043e3d1af3cc2b97f8da59a4c0d08fd0a95d7920526cbf426ea692383
Timestamp: 1673059226 Timestamp [UTC]: 2023-01-07 02:40:26 Age [y:d:h:m:s]: 03:130:23:20:45
Block: 669247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 866287 RingCT/type: yes/0
Extra: 0144e5022043e3d1af3cc2b97f8da59a4c0d08fd0a95d7920526cbf426ea69238302110000000352542ceb000000000000000000

1 output(s) for total of 0.003719690707 xmr

stealth address amount amount idx tag
00: ae591ad7f6de05a5218acc6379f3aaa0eae1746c69cc181a5ca474ced81114da 0.003719690707 1110550 of 0 -

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": 669257, "vin": [ { "gen": { "height": 669247 } } ], "vout": [ { "amount": 3719690707, "target": { "key": "ae591ad7f6de05a5218acc6379f3aaa0eae1746c69cc181a5ca474ced81114da" } } ], "extra": [ 1, 68, 229, 2, 32, 67, 227, 209, 175, 60, 194, 185, 127, 141, 165, 154, 76, 13, 8, 253, 10, 149, 215, 146, 5, 38, 203, 244, 38, 234, 105, 35, 131, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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: