Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233de31cd7f69d86509dac9e81262f0ad85b382da9fa56bcbf4f2b04ef40d04e

Tx prefix hash: ea4fe15c5728e3c95f7779eb81c4a6657822f60d68c0d4d7446c2cb6d6e6e949
Tx public key: ea73453703e276b281b89824cb8b49f2055befe3c22a55f80ae85b783a29ef24
Timestamp: 1701955273 Timestamp [UCT]: 2023-12-07 13:21:13 Age [y:d:h:m:s]: 01:190:17:58:11
Block: 907954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397432 RingCT/type: yes/0
Extra: 01ea73453703e276b281b89824cb8b49f2055befe3c22a55f80ae85b783a29ef2402110000000339e1d5d3000000000000000000

1 output(s) for total of 0.601965304000 dcy

stealth address amount amount idx
00: f88f796f35d6e851eae0e7cb62e5f375d1097d5bb36a10c303d4333f8dcc0ca7 0.601965304000 1364951 of 0

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 dinasty-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": 907964, "vin": [ { "gen": { "height": 907954 } } ], "vout": [ { "amount": 601965304, "target": { "key": "f88f796f35d6e851eae0e7cb62e5f375d1097d5bb36a10c303d4333f8dcc0ca7" } } ], "extra": [ 1, 234, 115, 69, 55, 3, 226, 118, 178, 129, 184, 152, 36, 203, 139, 73, 242, 5, 91, 239, 227, 194, 42, 85, 248, 10, 232, 91, 120, 58, 41, 239, 36, 2, 17, 0, 0, 0, 3, 57, 225, 213, 211, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8