Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f5fe82f4c8ad19ab49e2a7803132b15ec30135ccbbfbf9e3c7361cfc53dd80

Tx prefix hash: a906d64d77081d5e7eb689442a1bfdc9226eb4ca210aee3d7b81c49751575f52
Tx public key: bb5997fda8c5e52ed4bc0d739cda72433525551a5f1b461d892cadd1b7e04ceb
Timestamp: 1745638986 Timestamp [UTC]: 2025-04-26 03:43:06 Age [y:d:h:m:s]: 01:023:16:40:35
Block: 1269597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268900 RingCT/type: yes/0
Extra: 01bb5997fda8c5e52ed4bc0d739cda72433525551a5f1b461d892cadd1b7e04ceb02110000000601491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80fc49727735e22bcdda4c219a19d302000e834c4fe3288e28bbde8d20e70a5b 0.000600000000 1756836 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": 1269607, "vin": [ { "gen": { "height": 1269597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80fc49727735e22bcdda4c219a19d302000e834c4fe3288e28bbde8d20e70a5b" } } ], "extra": [ 1, 187, 89, 151, 253, 168, 197, 229, 46, 212, 188, 13, 115, 156, 218, 114, 67, 53, 37, 85, 26, 95, 27, 70, 29, 137, 44, 173, 209, 183, 224, 76, 235, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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: