Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b28da60594d8ffab5d0fa329564e4727a5f565a2af82d30908a178717d26e02a

Tx prefix hash: 2f814729ab2bdc632ca9ffbb8c80aa275370b944c7338cb9f34d0bd4b61ddba4
Tx public key: 432bc49109566b2c1f56b03904cad04331a474a27b4432546db6a65ec8b368cc
Timestamp: 1704484149 Timestamp [UTC]: 2024-01-05 19:49:09 Age [y:d:h:m:s]: 02:321:03:55:53
Block: 928908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754586 RingCT/type: yes/0
Extra: 01432bc49109566b2c1f56b03904cad04331a474a27b4432546db6a65ec8b368cc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b812f153b6c271859b4f30b2caa76a2003dd38778a2f6d07d072933312bb97b8 0.000600000000 1386774 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": 928918, "vin": [ { "gen": { "height": 928908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b812f153b6c271859b4f30b2caa76a2003dd38778a2f6d07d072933312bb97b8" } } ], "extra": [ 1, 67, 43, 196, 145, 9, 86, 107, 44, 31, 86, 176, 57, 4, 202, 208, 67, 49, 164, 116, 162, 123, 68, 50, 84, 109, 182, 166, 94, 200, 179, 104, 204, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: