Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf160f8cf23ab6c7af7482a93d8cea58ccbd3a7adfb97ebcbf1be67d8828b7f1

Tx prefix hash: fc2a93041851d9832fde1db4c2f2c8c22cc411a09ece66b47a94d65a70c466ba
Tx public key: 6b611ad374bbb4a28cac250240722f1f858c4cede5eede47fff792d74de98095
Timestamp: 1774899992 Timestamp [UTC]: 2026-03-30 19:46:32 Age [y:d:h:m:s]: 00:231:08:04:33
Block: 1509291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170831 RingCT/type: yes/0
Extra: 016b611ad374bbb4a28cac250240722f1f858c4cede5eede47fff792d74de98095021100000002ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9651c8f20483d6eeb4dd9aab00945e8ba7f9c71015e96274e2caccd0277bcba8 0.000600000000 1999063 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": 1509301, "vin": [ { "gen": { "height": 1509291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9651c8f20483d6eeb4dd9aab00945e8ba7f9c71015e96274e2caccd0277bcba8" } } ], "extra": [ 1, 107, 97, 26, 211, 116, 187, 180, 162, 140, 172, 37, 2, 64, 114, 47, 31, 133, 140, 76, 237, 229, 238, 222, 71, 255, 247, 146, 215, 77, 233, 128, 149, 2, 17, 0, 0, 0, 2, 238, 75, 113, 129, 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: