Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79af60773cee6d341b58a604df3f8f2ae81f7214bd6c75d5ef0023eba50c2d5

Tx prefix hash: 511f21eb71c98d4d58bfe01669e00e736b895d9e7ad0a8afff743ad7039d86f9
Tx public key: a4b1211130ea5524d9133c350dfa3a58e177fb481f8c31580039035089741368
Timestamp: 1769631867 Timestamp [UTC]: 2026-01-28 20:24:27 Age [y:d:h:m:s]: 00:053:01:38:28
Block: 1465698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37929 RingCT/type: yes/0
Extra: 01a4b1211130ea5524d9133c350dfa3a58e177fb481f8c31580039035089741368021100000007215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 50abab1b0e552d387123f8e2ec049eec4378c71b4edd4ca40b8813abb35cb274 0.000600000000 1954928 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": 1465708, "vin": [ { "gen": { "height": 1465698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50abab1b0e552d387123f8e2ec049eec4378c71b4edd4ca40b8813abb35cb274" } } ], "extra": [ 1, 164, 177, 33, 17, 48, 234, 85, 36, 217, 19, 60, 53, 13, 250, 58, 88, 225, 119, 251, 72, 31, 140, 49, 88, 0, 57, 3, 80, 137, 116, 19, 104, 2, 17, 0, 0, 0, 7, 33, 91, 191, 137, 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