Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31ad7da3231c06f0486a59abc660f0e39d95184b87b01b17e5d6dba80f37dae5

Tx prefix hash: 7f0d3b9ae5b49c86ab3154b16eadbdae77dc8c3bdb92c8f3086c38754b2a2680
Tx public key: c769db56997dc9833ce033593853bdb6f559817f4ff78d6149c8393c6cc907a3
Timestamp: 1735787595 Timestamp [UTC]: 2025-01-02 03:13:15 Age [y:d:h:m:s]: 01:132:05:00:06
Block: 1188308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345158 RingCT/type: yes/0
Extra: 01c769db56997dc9833ce033593853bdb6f559817f4ff78d6149c8393c6cc907a3021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf917e3ab87ed6fc7b8e2c87f50378f189c3ef918a853ec3e4c0bdb854ac9755 0.000600000000 1674809 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": 1188318, "vin": [ { "gen": { "height": 1188308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf917e3ab87ed6fc7b8e2c87f50378f189c3ef918a853ec3e4c0bdb854ac9755" } } ], "extra": [ 1, 199, 105, 219, 86, 153, 125, 201, 131, 60, 224, 51, 89, 56, 83, 189, 182, 245, 89, 129, 127, 79, 247, 141, 97, 73, 200, 57, 60, 108, 201, 7, 163, 2, 17, 0, 0, 0, 1, 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: