Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f95c7b5c9905ff20c5d15c4d8acd31009ff1a4737f2ffda15a4830c8661207

Tx prefix hash: 3a34e8945d528f7de00098e5f2abb8dd5c51214d94acdbd7f711c9d342fe24d3
Tx public key: 8bdb794368dc3018db8dcfff1133ce8d3c329788fa165f7d396569a601fbc6ae
Timestamp: 1716647748 Timestamp [UCT]: 2024-05-25 14:35:48 Age [y:d:h:m:s]: 00:295:20:36:38
Block: 1029768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211466 RingCT/type: yes/0
Extra: 018bdb794368dc3018db8dcfff1133ce8d3c329788fa165f7d396569a601fbc6ae02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b39309c77dad7b33b3f54c5cb0647209ae026698e212c455a3df7ac7e18cd078 0.600000000000 1497949 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 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": 1029778, "vin": [ { "gen": { "height": 1029768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b39309c77dad7b33b3f54c5cb0647209ae026698e212c455a3df7ac7e18cd078" } } ], "extra": [ 1, 139, 219, 121, 67, 104, 220, 48, 24, 219, 141, 207, 255, 17, 51, 206, 141, 60, 50, 151, 136, 250, 22, 95, 125, 57, 101, 105, 166, 1, 251, 198, 174, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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